Memory system and method of controlling memory system

ABSTRACT

According to one embodiment, a memory system includes a non-volatile semiconductor memory, a block management unit, and a transcription unit. The semiconductor memory includes a plurality of blocks to which data can be written in both the first mode and the second mode. The block management unit manages a block that stores therein no valid data as a free block. When the number of free blocks managed by the block management unit is smaller than or equal to a predetermined threshold value, the transcription unit selects one or more used blocks that stores therein valid data as transcription source blocks and transcribes valid data stored in the transcription source blocks to free blocks in the second mode.

CROSS-REFERENCE TO RELATED APPLICATIONS

This is a continuation application of U.S. application Ser. No.17/018,956 filed Sep. 11, 2020, which is a continuation application ofU.S. application Ser. No. 16/044,257 filed Jul. 24, 2018, (now U.S. Pat.No. 10,871,900 issued Dec. 22, 2020), which is a continuationapplication of U.S. application Ser. No. 15/880,168 filed Jan. 25, 2018,(now U.S. Pat. No. 10,055,132 issued Aug. 21, 2018), which is acontinuation of U.S. application Ser. No. 15/391,184 filed Dec. 27,2016, (now U.S. Pat. No. 9,910,597 issued Mar. 6, 2018), which is acontinuation of U.S. application Ser. No. 14/467,685 filed Aug. 25,2014, (now U.S. Pat. No. 10,877,664, issued Dec. 29, 2020), which is acontinuation of U.S. application Ser. No. 13/038,681 filed Mar. 2, 2011(now U.S. Pat. No. 8,832,357 issued Sep. 9, 2014), which is based uponand claims the benefit of priority from Japanese Patent Application No.2010-214221, filed Sep. 24, 2010, the entire contents of each of whichare incorporated herein by reference.

FIELD

Embodiments described herein relate generally to a memory system.

BACKGROUND

As a technique to expand the capacity of a NAND flash memory, there is amulti-level recording (MLC: Multi-Level Cell) method. In thisdisclosure, a flash memory of the MLC method is referred to as an MLCflash memory, and a flash memory of a binary recording (SLC:Single-Level Cell) method is referred to as an SLC flash memory. In theSLC method (hereinafter referred to as SLC mode), one bit is recorded inone cell which is a unit of recording. On the other hand, in the MLCmethod (hereinafter referred to as MLC mode), N bits (N>1) can berecorded in one cell. Therefore, for example, in an MLC flash memory oftwo-bit recording, one cell can represent four values, and in an MLCflash memory of three-bit recording, one cell can represent eightvalues.

Such flash memories that can store relatively large amount ofinformation in a certain storage area can have the recording capacityper volume larger than that of a flash memory that can store relativelysmall amount of information in the same storage area, and have a meritthat the cost per storage capacity can be reduced. In contrast, a flashmemory that can store relatively small amount of information in acertain storage area has a merit that the access time for reading andwriting is short and the memory has high reliability compared with aflash memory that can store relatively large amount of information inthe same storage area.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a diagram (1) showing a use example of a block of a firstembodiment;

FIG. 2 is a diagram (2) showing a use example of a block of theembodiment;

FIG. 3 is a diagram (3) showing a use example of a block of theembodiment;

FIG. 4 is an external view of a personal computer of the embodiment;

FIG. 5 is a block diagram of a memory system of the embodiment;

FIG. 6 is a data structure example of an address translation table ofthe embodiment;

FIG. 7 is an example of a reverse table of the embodiment;

FIG. 8 is an illustration of a mapping update when data is written inthe embodiment (before update);

FIG. 9 is an illustration of a mapping update when data is written inthe embodiment (after update);

FIG. 10 is an illustration of a mapping update when data is deleted inthe embodiment (before deletion);

FIG. 11 is an illustration of a mapping update when data is deleted inthe embodiment (after deletion);

FIG. 12 is an illustration of a mapping update when data is transcribedin the embodiment (before transcription);

FIG. 13 is an illustration of a mapping update when data is transcribedin the embodiment (after transcription);

FIG. 14 is a schematic flowchart when a data write request is receivedin the embodiment;

FIG. 15 is a schematic flowchart (1) of the used block reductionprocessing in the embodiment;

FIG. 16A is a schematic flowchart (2) of the used block reductionprocessing in the embodiment;

FIG. 16B is a schematic flowchart (3) of the used block reductionprocessing in the embodiment;

FIG. 17 is a schematic flowchart (1) of transcription source block groupselection processing in the embodiment;

FIG. 18 is a schematic flowchart (2) of transcription source block groupselection processing in the embodiment;

FIG. 19 is a schematic flowchart (3) of transcription source block groupselection processing in the embodiment;

FIG. 20 is a simulation result of random write in the embodiment;

FIG. 21 is a block diagram of a memory system of a second embodiment;and

FIG. 22 is a schematic flowchart of execution of the used blocksreduction processing in the embodiment.

DETAILED DESCRIPTION

According to one embodiment, a memory system includes a non-volatilesemiconductor memory, a first storage unit, a second storage unit, athird storage unit, a first receiving unit, an acquisition unit, a firstwrite unit, a selection unit, a second write unit, a managementinformation update unit, a second receiving unit, and a read unit. Thenon-volatile semiconductor memory includes a plurality of first storageareas, and is capable of having one or more second storage areas whichare included in the plurality of first storage areas and in which novalid data is stored, a plurality of third storage areas which areincluded in the plurality of first storage areas and which are obtainedby copying and storing therein data received from a host, and aplurality of fourth storage areas which are obtained by copying andstoring therein data stored in the third storage areas or stored in thefourth storage areas. The valid data is data stored at a physicaladdress associated with a logical address. The logical address is anaddress specified from the host. The physical address indicates a datastorage position in a storage area of a semiconductor memory. The firststorage unit stores therein first management information that indicateswhich area of the plurality of first storage areas is the second storagearea. The second storage unit stores therein second managementinformation that indicates which areas of the plurality of first storageareas are the third storage areas. The third storage unit stores thereinthird management information that indicates which areas of the pluralityof first storage areas are the fourth storage areas. The first receivingunit receives write request data which is data requested to be writtenby the host. The acquisition unit acquires one second storage area fromthe one or more second storage areas on the basis of the firstmanagement information. The first write unit writes the write requestdata to the second storage area acquired by the acquisition unit in afirst mode. When the number of the second storage areas is smaller thanor equal to a first threshold value, the selection unit selects one ormore storage areas from the plurality of third storage areas on thebasis of the second management information or select one or more storageareas from the plurality of fourth storage areas on the basis of thethird management information. The second write unit writes valid datastored in the storage area selected by the selection unit to the secondstorage area acquired by the acquisition unit in a second mode. When thesecond write unit writes the valid data, the management informationupdate unit deletes the selected storage area from the second managementinformation or the third management information and adds the selectedstorage area to the first management information. The second receivingunit receives a read request of data from the host. The read unit readsdata in the first mode when data requested to be read by the readrequest is written to the third storage area and reads data in thesecond mode when data requested to be read by the read request iswritten to the fourth storage area. A write speed or a read speed in thefirst mode is faster than that in the second mode. A maximum amount ofinformation that can be written in a same storage area in the first modeis smaller than that in the second mode.

Various embodiments will be described hereinafter with reference to theaccompanying drawings.

First, a memory system 1 according to a first embodiment will bedescribed in detail with reference to the drawings. FIGS. 1 to 3 arediagrams showing a use example of blocks according to the firstembodiment.

A NAND flash memory used in the first embodiment is a flash memory 112that can change operation mode of writing data. For example, the flashmemory is an MLC flash memory that can change operation mode of writingdata. As the operation mode, a first operation mode and a secondoperation mode are used. In the first operation mode, the amount ofinformation written to a certain storage area is smaller than that inthe second operation mode (in other words, in the second operation mode,the amount of information written to a certain storage area is greaterthan that in the first operation mode). For example, the secondoperation mode is a mode in which the number of bits that can be writtento one cell is greater than that in the first operation mode. In a morespecific example, the first operation mode is an SLC mode or an MLCmode. The second operation mode is an MLC mode in which the number ofbits that can be written to one cell is greater than that in the firstoperation mode. In the description below, it is assumed that the firstoperation mode is the SLC mode and the second operation mode is the MLCmode. However, the MLC mode is not limited to a single mode, but theremay be a plurality of MLC modes. For example, the MLC mode may bechanged between four-value mode and eight-value mode.

A storage area of not only the MLC flash memory 112 but also a NANDflash memory includes a plurality of blocks (first storage areas). Theblock is a predetermined unit of storage area, and a unit of data to beerased. Therefore, when newly writing data to a block, data in the blockneeds to be collectively erased in advance.

Each block includes a plural of pages. Data is written and read to andfrom each page. There is a rule of an order of writing data to pages.Therefore, after erasing data in a block, it is necessary to write datato the block in a specific page order. In other words, after data iswritten to a block, it is impossible to overwrite data to a specificpage without erasing data in the block, and even after erasing data fromthe block, it is impossible to write data to a random page in the block.

The operation mode of each NAND flash memory can be set independentlyfor each block. However, operation modes of each page in a block need tobe the same. Therefore, operation mode cannot be switched between thepages. In other words, after data is written to a page in a block, theoperation mode of the block cannot be switched until the data in theblock is collectively erased.

The amount of data that can be written to a block is different amongeach operation mode. In other words, the capacity of a block(hereinafter referred to as block capacity) varies depending on theoperation mode.

Specifically, the page size of each page does not vary, and the numberof pages varies. For example, in an MLC flash memory of two-bitrecording method, an SLC block of two-value mode has the number of pagesand the block capacity that are ½ times of those of an MLC block offour-value mode.

In the first embodiment, as shown in FIGS. 1 to 3, as the type of block,there are free blocks (second storage area) B_free in which no validdata is stored and used blocks in which valid data is stored. Among theused blocks, there are blocks B_slc which is obtained by copying andstoring therein valid data written in the first operation mode andblocks B_mlc which is obtained by copying and storing therein datawritten in the second operation mode. Herein, the block B_slc isreferred to as an SLC block B_slc (third storage area), and the blockB_mlc is referred to as an MLC block B_mlc (fourth storage area).

The blocks are classified into groups, and managed. For example, thefree block B_free is classified into a free block group G_free andmanaged, the SLC block B_slc is classified into an SLC block group G_slc(fifth storage area) and managed, and the MLC block B_mlc is classifiedinto an MLC block group G_mlc (sixth storage area) and managed.

In the first embodiment, as shown in FIG. 1, when a request of writingdata D1 is issued from a host device, the data D1 is written in the SLCmode to a free block B_free which is assigned in advance as a block towhich new data is to be written. A new data written block B_D1 to whichthe data D1 is written is registered as the SLC block group G_slc. As aresult, the number of free blocks B_free managed in the free block groupG_free decreases by 1, and instead of that, the number of SLC blocksB_slc managed in the SLC block group G_slc increases by 1. The writingof data in the SLC mode is performed without being limited by the totaldata capacity of the SLC blocks B_slc managed in the SLC block groupG_slc. In other words, in the first embodiment, the number of SLC blocksB_slc has no upper limit and is variable. Based on this, in the firstembodiment, a variable-length SLC buffer is implemented. Further, in thefirst embodiment, the number of blocks, whose total capacity is greaterthan or equal to a surplus capacity (generally referred to asOver-Provisioning) obtained by subtracting the logical capacity that isa maximum capacity provided to the host device from the total storagecapacity of the MLC flash memory, can be managed as the SLC blocksB_slc. However, as described below, a lower limit may be set to thenumber of the free blocks B_free managed by the free block group G_free.

Thereafter, for example, when the number of the free blocks B_freebelonging to the free block group G_free becomes smaller than or equalto a predetermined threshold value Tbf by writing data from the hostdevice, in the first embodiment, as shown in FIG. 2, some of the SLCblocks B_slc belonging to the SLC block group G_slc are selected, anddata stored in these SLC blocks B_slc as valid data (hereinafterreferred to as valid data) is written in the MLC mode to a free blockB_free assigned in advance as a transcription destination block(transcription). The transcription destination block B_Dts to which thevalid data is written is registered as the MLC block group G_mlc. As aresult, the number of the used blocks decreases, and the number of thefree blocks B_free increases. Here, as an SLC block B_slc to betranscribed, it is desired to select an SLC block B_slc in which theamount of valid data (rate of valid data) is small with respect to theblock capacity and an SLC block B_slc which does not store data that isfrequently updated.

Thereafter, in a state in which the number of the MLC blocks B_mlcbelonging to the MLC block group G_mlc has increased by the datatranscription, when the number of the free blocks B_free becomes smallerthan or equal to the predetermined threshold value Tbf, in the firstembodiment, as shown in FIG. 3, either the SLC block group G_slc or theMLC block group G_mlc is selected, some of blocks belonging to theselected block group are selected, and valid data in the selected blocksis written in the MLC mode to a free block B_free assigned in advance asa transcription destination block (transcription). The transcriptiondestination block B_Dts or B_Dtm to which the valid data is written isregistered as the MLC block group G_mlc. As a result, the number of theused blocks decreases, and the number of the free blocks B_freeincreases. Here, as a used block to be transcribed, it is desired toselect a block in which the amount of valid data (rate of valid data) issmall with respect to the block capacity and a block which does notstore data that is frequently updated. As blocks to be transcribed, forexample, blocks of the same operation mode are selected. Specifically, aset of SLC blocks B_slc or a set of MLC blocks B_mlc is selected.

It is possible to determine which block group is selected on the basisof various parameters such as the total amount of valid data and thetotal rate of valid data of the blocks belonging to each block group.For example, as shown in FIGS. 1 and 2, when the total amount of validdata is small, it is possible to raise the ratio of the SLC blocks B_slcbecause all data can be recorded even if the sum of the block capacitiesis small. On the other hand, as shown in FIG. 3, when the total amountof valid data is large, it is necessary to raise the ratio of the MLCblocks B_mlc to increase the sum of the block capacities.

Further, when there is locality in LBA (Logical Block Address) of thedata written from the host, in other words, when the data is intensivelywritten to a range of specific LBAs, it is highly likely that the datais overwritten from the host before the data is transcribed from the SLCblock B_slc to the MLC block B_mlc and the old data in the SLC blockB_slc becomes invalid data. In the manner as described above, when thetotal rate of valid data in the SLC block group G_slc decreases, it isdesired that the SLC block group G_slc is selected as the block group tobe transcribed. In contrast, for example, when the locality moves, inother words, immediately after the range of LBAs to which the data isintensively written has moved to another range, it is highly likely thatthe data is overwritten from the host after the data is transcribed tothe MLC block B_mlc and the old data in the MLC block B_mlc becomesinvalid data. In the manner as described above, when the total rate ofvalid data in the MLC block group G_mlc decreases, it is desired thatthe MLC block group G_mlc is selected as the block group to betranscribed.

Here, the threshold value Tbf is a value obtained by experiments,experiences, or simulations in order to implement efficient data accessfrom the host device. For example, if the threshold value Tbf is toolarge, at a certain time point, the number of blocks which actuallystore data decreases and the total rate of valid data increases, so thatthe efficiency of transcription degrades. The threshold value Tbf needsto be at least the number of free blocks allocated at the same time forthe transcription processing.

Further, the trigger of performing data transcription is not limited tothe method using the threshold value Tbf. For example, the datatranscription may be performed periodically, or the data transcriptionmay be performed on the basis of a time period when there is no accessfrom the host device.

Next, a configuration and an operation of the memory system 1 will bedescribed. FIG. 4 is a schematic diagram showing an example of aninformation processing apparatus in which the memory system according tothe first embodiment can be mounted. A personal computer 10 illustratedin FIG. 4 mainly includes a main body 11 and a display unit 12. The mainbody 11 includes, for example, a housing 15, a keyboard 16, a touchpad17 which is a pointing device, an external interface 18 such as a cardslot to which a memory card 19 or the like can be attached and detachedand a USB (Universal Serial Bus), a main circuit board, and the memorysystem 1 which is an SSD (Solid State Drive).

On the main circuit board, main components such as a CPU (CentralProcessing Unit), a ROM (Read Only Memory), a RAM (Random AccessMemory), a Northbridge, and a Southbridge are mounted. In addition, themain body 11 may include an ODD (Optical Disk Drive) unit, variousexternal interfaces, and the like.

The display unit 12 includes a display housing 13 and a display device14 contained in the display housing 13. Although, in FIG. 4, a notebooktype personal computer is used as an example, the information processingapparatus in which the memory system according to the first embodimentcan be mounted is not limited to this. In other words, the memory systemaccording to the first embodiment and another embodiment described belowcan be applied to any computer where a flash memory can be mounted orattached as storage.

In FIG. 4, the memory system 1 is a storage device using a rewritablenon-volatile memory as a recording medium. The memory system 1 may bebuilt into the personal computer 10 or externally connected to thepersonal computer 10 via the external interface 18. Hereinafter, thememory system 1 according to the first embodiment will be described indetail with reference to the drawings.

As shown in FIG. 5, the memory system 1 roughly includes a controllerunit 100, a non-volatile memory unit 110, a buffer memory unit 120, andan interface unit 130. Each unit 100 to 130 can be connected to eachother via a signal line 140 such as a bus or a point-to-point line. Ahost device 150 such as a personal computer or a workstation thatrequests writing and reading of data to and from the non-volatile memoryunit 110 can also be connected to the signal line 140.

The interface unit 130 is, for example, a SATA (Serial ATA) interface,and communicates with the host device 150 via the signal line 140.However, the interface unit 130 is not limited to the SATA interface,but various interfaces such as a parallel ATA interface can be appliedto the interface unit 130. The interface unit 130 receives commands suchas read, write, flush, and deletion of data (e.g., the SATA TRIMcommand) from the host device 150 (first receiving unit and secondreceiving unit), and transmits a notification of receiving command tothe controller unit 100. The interface unit 130 transmits and receivesdata to and from the host device 150 in accordance with an instructionfrom the controller unit 100.

For the buffer memory unit 120, a high-speed memory having high randomaccessibility such as SRAM and DRAM is used. The buffer memory unit 120need not be a non-volatile memory. The buffer memory unit 120temporarily stores therein data transmitted or received to or from thehost device 150 by the interface unit 130 and data read or written fromor to the non-volatile memory unit 110 by the interface unit 130. Thebuffer memory unit 120 may store therein information for variousmanagement operations in addition to data.

The non-volatile memory unit 110 includes one or more MLC flash memories112 and a NAND controller 111. The MLC flash memory 112 is, for example,a NAND flash memory. One MLC flash memory 112 may be formed in one chip.Usually, the total storage capacity of the non-volatile memory unit 110needs to be greater than the logical capacity (maximum capacity providedto the host device). Therefore, the non-volatile memory unit 110 caninclude a plurality of MLC flash memories 112 according to the totalstorage capacity. It is desired that the NAND controller 111 cantransmit data to a plurality of MLC flash memories 112 in parallel. Thisis effective when the data transmission performance required as an SSDcannot be satisfied by using one MLC flash memory 112.

The description returns to FIG. 5. The controller unit 100 has functionsto manage user data and control each unit. The controller unit 100 maybe a SoC (System on a Chip) in which these functions are implemented asa circuit. The controller unit 100 may be implemented by a generalpurpose hardware processor executing software for implementing thesefunctions.

As these function blocks, the controller unit 100 includes an addresstranslation table storage unit 101, a block management unit 102, a validdata amount management unit 103, a read command processing unit 104, awrite command processing unit 105, a deletion command processing unit106, a block reduction processing unit 107, a transcription source blockgroup selection unit 108, and a transcription source block selectionunit 109 (transcription unit).

The address translation table storage unit 101 stores therein an addresstranslation table 101A holding a mapping between logical addressesspecified from the host device 150 and data recording positions in thememory system 1. When the host device 150 writes or deletes data of acertain logical address or the data is transcribed in the memory system1, the mapping of the logical address in the address translation table101A is updated. As a result, data in the new recording position becomesvalid data, and data in the old recording position becomes invalid data.When the mapping is updated, the update of the amount of valid data ineach block is notified to the valid data amount management unit 103.

The block management unit 102 manages block groups for classifying andmanaging blocks. A block can be classified into a free block or a usedblock depending on whether or not the block stores therein valid data.The used block can be classified into either an SLC block or an MLCblock depending on the write operation mode of valid data to the block.The block management unit 102 assigns a block in which no valid data isstored to a free block group, assigns a block in which valid datawritten in the SLC mode is stored to an SLC block group, and assigns ablock in which valid data written in the MLC mode is stored to an MLCblock group. The block management unit 102 holds information of blocksand the number of the blocks included in each block group as managementinformation of each block group. An operation mode of a free block isnot determined, and after the free block is obtained for use, theoperation mode is determined in accordance with the purpose of use. Themanagement information of each block group has a data structure thatenables all the blocks to be collectively registered as a specific blockgroup. For example, even when all the blocks are used in the SLC mode,all the blocks can be registered as the SLC block group. The blockmanagement unit 102 updates information indicating which block belongsto which block group (free, SLC, or MLC) (management information updateunit).

When the valid data amount management unit 103 receives the notificationof the update of the amount of valid data in each block from the addresstranslation table 101A, the valid data amount management unit 103calculates the total amount of valid data of the blocks included in theSLC block group and the MLC block group.

When the read command processing unit 104 receives a notification ofreceiving the read command from the interface unit 130, the read commandprocessing unit 104 searches the address translation table 101A for arecording position in the non-volatile memory unit 110 corresponding toa logical address specified by the read command, and reads data recordedin the recording position to the buffer memory unit 120 (reading unit).In this way, data in a range specified by the read command istemporarily stored in the buffer memory unit 120. Thereafter, the readcommand processing unit 104 controls the interface unit 130 to transmitthe data temporarily stored in the buffer memory unit 120 to the hostdevice 150.

When the write command processing unit 105 receives a notification ofreceiving the write command from the interface unit 130, the writecommand processing unit 105 allocates a free space in the buffer memoryunit 120 and controls the interface unit 130 to receive data from thehost device 150. Thereafter, when a sufficient amount of data isaccumulated in the buffer memory unit 120, the write command processingunit 105 writes the data in the buffer memory unit 120 to a block towhich new data is to be written. Thereafter, the write commandprocessing unit 105 updates the mapping by registering a recordingposition corresponding to a logical address of the written data into theaddress translation table 101A. The write command processing unit 105acquires a free block as a block to which new data is to be written fromthe block management unit 102 (acquisition unit), and uses the block towhich new data is to be written as an SLC block (first writing unit).When the write command processing unit 105 acquires a free block as ablock to which new data is to be written from the block management unit102, if the number of remaining free blocks is smaller than apredetermined threshold value, the write command processing unit 105sends a number-of-used-blocks reduction request to the block reductionprocessing unit 107.

When the deletion command processing unit 106 receives a notification ofreceiving the deletion command from the interface unit 130, the deletioncommand processing unit 106 updates the mapping of the addresstranslation table 101A so that data in a recording positioncorresponding to a specified logical address is invalidated.

The block reduction processing unit 107 selects at least one used block(hereinafter referred to as “transcription source block”) among usedblocks which store therein valid data (selection unit), and transcribesvalid data in the selected transcription source blocks to a free block(second writing unit). The block group from which the number of blocksis reduced is selected by the transcription source block group selectionunit 108. The transcription source blocks are selected by thetranscription source block selection unit 109.

The block reduction processing unit 107 collects, as new free blocks,the transcription source blocks that become free blocks as a result ofthe transcription of the valid data, namely, the transcription sourceblocks whose amount of valid data becomes “0”. The mapping of thetranscribed data is updated by registering the recording position of thetranscription destination corresponding to the logical address of thetranscribed data into the address translation table 101A. Here, adifference between the number of the transcription source blockscollected as new free blocks and the number of free blocks assigned asblocks of transcription destination (hereinafter referred to as“transcription destination block”) is the number of reduced used blocks.As the transcription source blocks, it is desired that blocks of thesame operation mode are selected. The free block assigned as thetranscription destination block is desired to be used in the MLC mode.

The transcription source block group selection unit 108 selects eitherthe SLC block group or the MLC block group, from which the number ofblocks is reduced. The transcription source block group selection unit108 selects the block group from which the number of blocks is reducedon the basis of, for example, the rate of valid data in each block groupor in one of the block groups. The transcription source block groupselection unit 108 can calculate the rate of valid data in a block groupfrom the number of blocks in each block group referred from the blockmanagement unit 102 and the amount of valid data in each block or ineach block group referred from the valid data amount management unit103. Specifically, the transcription source block group selection unit108 can obtain the rate of valid data in a block group by calculatingthe total capacity of each block group from the operation mode and thenumber of blocks in each block group and dividing the amount of validdata in each block group by the calculated total capacity.

The transcription source block selection unit 109 selects one or moreused blocks as the transcription source blocks from the transcriptionsource block group selected by the transcription source block groupselection unit 108. The transcription source block selection unit 109preferentially selects a block having a low rate of valid data among theused blocks belonging to the transcription source block group.Alternatively, the transcription source block selection unit 109 maypreferentially select a used block having a rate of valid data smallerthan a threshold value, which is the same as the threshold value of therate of valid data in the MLC block group, which is used when thetranscription source block group selection unit 108 selects thetranscription source block group. Further, when the transcription sourceblock group is the SLC block group, the blocks may be selected simply inthe order of FIFO, in other words, the SLC blocks may be selected in thetime-series order of writing.

Next, a unit of data management and the address translation table willbe described in detail with reference to the drawings. Generally, a unitof data management when accessing from the host device 150 to a storageapparatus is called “sector”, and the size of the sector is 512 bytes.In a storage area provided from the storage apparatus such as an HDD andan SSD to the host device 150, continuous logical addresses are providedto each sector sequentially from the top of the area. Generally, thelogical address is called “LBA” (Logical Block Address).

On the other hand, a unit of data management in the memory system 1according to the first embodiment is called “cluster”. The size of thecluster can be larger than the size of the sector. When the size of thecluster is larger than the size of the sector, it is possible to reducethe number of entries and the amount of processing in the addresstranslation table 101A. For example, when one cluster includes eightsectors, each cluster includes continuous eight sectors starting from asector having a logical address that is a multiple of eight. As aresult, the size of the cluster is 4 KB (kilo byte). In the descriptionbelow, an example will be described, in which a unit of data managementin the memory system 1 is the cluster, the logical address of eachcluster is an LBA of the first sector of the cluster, and the size ofthe cluster is 4 KB. However, the size of the cluster can be changedaccording to purpose or the like. Of course, if an area for storingmanagement information of data can be sufficiently allocated, the sizeof the cluster may be the same as the size of the sector. In this case,data can be managed for each sector.

A plurality of pieces of cluster data is recorded in each page in ablock. As described above, data in a cluster is sector data havingcontinuous logical addresses. However, a plurality of pieces of clusterdata in a block is not necessarily cluster data having continuouslogical addresses. As described below, the mapping between logicaladdresses and recording positions in the memory system 1 is dynamicallydetermined depending on a sequence of writing from the host device 150and a sequence of transcription in the memory system 1.

Therefore, the address translation table 101A for managing the mappingbetween the logical addresses and the recording positions is provided.The address translation table 101A has functions for registering andinvalidating a recording position corresponding to a logical address andsearching the mapping. Also, the address translation table 101A has afunction for, when the mapping is updated, notifying the valid dataamount management unit 103 of a block identifier of a block (such as thesequential number of a block) corresponding to an updated recordingposition and a difference between the amounts of valid data in the blockbefore and after the update.

Various data structures can be applied to the address translation table101A that holds mapping information. FIG. 6 is an example of a simpledata structure of the address translation table. The data structureshown in FIG. 6 is a structure in which the address translation table101A that can store therein recording positions of all clusters in thelogical capacity holds recording positions of each cluster in the orderof logical addresses. For example, the table structure is prepared on amemory in advance. In the example shown in FIG. 6, the size of theclusters is 4 KB, the first logical address of each cluster data is amultiple of eight, and block identifier, page number, and offsetposition in page are held as a recording position.

In the example of the data structure shown in FIG. 6, when searching fora logical address from a recording position, it is necessary to searchfor an entry corresponding to the recording position from all theentries in the address translation table 101A. Therefore, the cost istoo much high. Therefore, the address translation table 101A mayadditionally hold a reverse table by which a logical address can bequickly searched from a recording position. FIG. 7 shows an example ofthe reverse table. In the example shown in FIG. 7, the reverse tableincludes sub-tables 101 b-1, 101 b-2, and so forth which record thereinlogical addresses corresponding to all the recording positions in eachblock and a main-table 101 a having pointers to the sub-tables 101 b-1,101 b-2, and so forth corresponding to each block.

Next, how the mapping in the address translation table 101A is updatedwhen data is written or deleted according to a request from the hostdevice 150 and data is transcribed in the memory system 1 will bedescribed in detail with reference to the drawings. In this description,it is assumed that the logical address of the write data specified fromthe host device 150 is 16.

FIGS. 8 and 9 are figures for explaining the update of the mapping whendata is written. In the example shown in FIG. 8, block “C”, page number“2”, and offset position in page “1” are registered as a recordingposition corresponding to the logical address “16” in the addresstranslation table 101A to which data has not yet been written. When apage size of data including data to be written to other logicaladdresses is transmitted from the host device 150 and accumulated in thebuffer memory unit 120, the write command processing unit 105 writes thepage size of data accumulated in the buffer memory unit 120 to anunwritten page “1” in a block “A” selected as a block to which new datais to be written.

After the data is written, as shown in FIG. 9, as a recording positioncorresponding to the logical address “16”, block “A”, page “1”, andoffset position in page “0” are registered in the address translationtable 101A by the write command processing unit 105. Based on this, themapping managed by the address translation table 101A is updated. As aresult, data in the old recording position becomes invalid data, anddata in the new recording position becomes valid data.

FIGS. 10 and 11 are figures for explaining the update of the mappingwhen data is deleted. In the update of the mapping when data is deleted,different from the update of the mapping when data is written, data isnot written to a block and only invalidation of the recording positioncorresponding to the logical address is performed in the addresstranslation table 101A. In the example shown in FIGS. 10 and 11, thedeletion command processing unit 106 invalidates the mapping (see FIG.11) by registering an invalid value (for example, a block identifierindicating no block) into the recording position of an entrycorresponding to the logical address “16” in the address translationtable 101A from which data has not yet been deleted (see FIG. 10). Basedon this, data in the old recording position in the block “C” becomesinvalid data.

FIGS. 12 and 13 are figures for explaining the update of the mappingwhen data is transcribed in the SSD. The difference between the updateof the mapping when data is written and the update of the mapping whendata is transcribed is whether or not the data to be written/transcribedis recorded in the memory system 1.

In the example shown in FIG. 12, before transcribing data, valid datacorresponding to the logical addresses “0”, “8”, and “16” are recordedin transcription source blocks “E” and “F”. The block reductionprocessing unit 107 sequentially checks whether or not data in eachrecording position is valid data in ascending order from the first pagein used blocks that are selected as the transcription source blocks byusing the address translation table 101A. The block reduction processingunit 107 sequentially reads the checked valid data in the transcriptionsource blocks “E” and “F” and outputs the read data to the buffer memoryunit 120, and thereafter, when a page size of data is accumulated in thebuffer memory unit 120, the block reduction processing unit 107transcribes the valid data to be transcribed by recording the page sizeof data into a transcription destination block “D” in units of a page.

After the data is transcribed, as shown in FIG. 13, the block reductionprocessing unit 107 registers the recording positions corresponding tothe logical addresses of the transcribed data into the addresstranslation table 101A. In the example shown in FIGS. 12 and 13, thevalid data corresponding to the logical addresses “0”, “8”, and “16” aretranscribed to the transcription destination block “D”, so that thepositions in the block “D” are registered into the address translationtable 101A as the recording positions of these logical addresses. As aresult, data in the old recording positions in the transcription sourceblocks “E” and “F” are invalidated.

If the reverse table is held in the address translation table 101A asshown in FIG. 7, the reverse table is also updated when the mapping isupdated as described above.

Next, block management according to the first embodiment will bedescribed in detail with reference to FIG. 5. The blocks are classifiedinto free blocks and used blocks. Since no valid data is recorded in afree block, it is possible to assign a free block as a block to whichdata is written when data is written next time. On the other hand, aused block has valid data. The used blocks are classified into the SLCblocks and the MLC blocks according to the operation mode thereof.

The block management unit 102 holds free block group managementinformation 102 a that is information indicating which blocks are freeblocks (first management information), SLC block group managementinformation 102 b that is information indicating which blocks are SLCblocks (second management information), and MLC block group managementinformation 102 c that is information indicating which blocks are MLCblocks (third management information), in addition to block managementinformation 102 d that manages each block. The management informationpieces (102 a to 102 c) of each block group include information of theblocks included in each block group and the number of the blocks.

The block management unit 102 may include a storage apparatus (firststorage unit) for storing therein the free block group managementinformation 102 a, a storage apparatus (second storage unit) for storingtherein the SLC block group management information 102 b, and a storageapparatus (third storage unit) for storing the MLC block groupmanagement information 102 c. Each of management information pieces maybe stored in a single storage apparatus included in the block managementunit 102, or the block management unit 102 may have a plurality ofstorage apparatuses and store each of management information pieces in astorage apparatus (storage unit) different from each other.

The block management unit 102 has functions to assign a free block,register a free block, register a used block, refer to the number ofblocks in a block group, and refer to block information.

In accordance with the operation mode of a block specified to beregistered, the function to register a used block adds information ofthe block to the SLC block group management information 102 b or the MLCblock group management information 102 c, and adds one to the number ofblocks of the block group.

The function to assign a free block refers to the free block groupmanagement information 102 a, selects a block included in the free blockgroup, and returns information of the selected free block to the writecommand processing unit 105 or the block reduction processing unit 107.Also, the function to assign a free block deletes the information of theselected free block from the free block group management information 102a, and subtracts one from the number of blocks of the free block group.

In accordance with the operation mode of a block specified to beregistered, the function to register a free block deletes information ofthe block from the SLC block group management information 102 b or theMLC block group management information 102 c, and subtracts one from thenumber of blocks of the block group. Thereafter, the function toregister a free block adds the information of the block to the freeblock group management information 102 a, and adds one to the number ofblocks of the block group. This function is used by the block reductionprocessing unit 107 when collecting, as a free block, a used block whosevalid data becomes “0” by transcription of data.

Here, various forms can be considered as a data structure of themanagement information of each block group. However, in the firstembodiment, as described above, the management information needs to havea data structure where the blocks can be managed even when all theblocks mounted in the memory system 1 are concentrated in one blockgroup. The reason to have such a data structure is to make it possibleto use all the blocks as the SLC blocks at the same time. Therefore, forexample, one of such data structures having a simplest structure is alist structure connecting nodes that store therein a block identifier.

In the first embodiment, it is possible to use one physical blockprovided by a NAND flash memory as one block without change, or form onelogical block by combining a plurality of physical blocks. For example,if a block capacity of one physical block (MLC mode) is 1 MB, the pagesize is 8 KB, and the number of pages is 128, when forming a logicalblock by collecting 32 physical blocks, the logical block can be handledas a block whose block capacity is 32 MB, page size is 256 KB, andnumber of pages is 128. In this case, a block identifier used in eachfunction block is a block identifier of logical block.

One of the merits of combining a plurality of physical blocks andhandling the combined physical blocks as one logical block is to reduceinformation of the blocks that should be managed by reducing the totalnumber of blocks. For example, in an SSD having a total storage capacityof 128 GB, the number of physical blocks is 131072 (=128×1024). On theother hand, the number of logical blocks in each of which 32 physicalblocks are combined is 4096. When a logical block is formed by combiningphysical blocks, all of which can be accessed in parallel, the accessspeed of one logical block can be improved.

Next, the valid data amount management unit 103 according to the firstembodiment will be described in detail with reference to the drawings.The valid data amount management unit 103 calculates the total amount ofvalid data of the blocks included in the SLC block group and the MLCblock group. By using the update notification from the addresstranslation table 101A as a trigger, the valid data amount managementunit 103 searches for a block group to which a block whose mapping isupdated belongs from the block management unit 102, and increases ordecreases the amount of valid data of the block group by usingdifference information included in the update notification. Here, thevalid data amount management unit 103 may hold information of the amountof valid data for each block. In the same manner as for the amount ofvalid data for each block group, the amount of valid data for each blockis increased or decreased by using difference information of valid dataof the block.

The valid data amount management unit 103 may not be an independentfunction unit. For example, the function of the valid data amountmanagement unit 103 can be included in the address translation table101A. Specifically, when the address translation table 101A includes thereverse table as shown in FIG. 7, the amount of valid data of each blockmay be registered in each sub-table 101 b-1, 102 b-2, and so forth. Oralternatively, the function of the valid data amount management unit 103can be included in the block management unit 102. In this case,information related to the amount of valid data of each block and eachblock group is registered in the block management unit 102.

Next, an operation of the memory system 1 according to the firstembodiment will be described in detail with reference to the drawings.FIG. 14 is a flowchart showing a schematic operation when a data writerequest is issued from the host device 150. In the operation shown inFIG. 14, it is assumed that a block to which new data is to be writtenhas been assigned as an initial state.

As shown in FIG. 14, first, the write command processing unit 105 waitsfor an input of a write command of new data to the interface unit 130from the host device 150 (NO in step S101). When receiving the writecommand (YES in step S101), the write command processing unit 105allocates a data storage area in the buffer memory unit 120 (step S102),and then stores the new data transmitted from the host device 150 in thedata storage area allocated in the buffer memory unit 120 (step S103).

Next, the write command processing unit 105 checks the amount ofunwritten new data stored in the buffer memory unit 120 (step S104), andwhen the amount of data is smaller than the page size (NO in step S104),the write command processing unit 105 returns to step S101 and waits forthe next write command. On the other hand, when the amount of data isgreater than or equal to the page size (YES in step S104), the writecommand processing unit 105 selects data corresponding to the page sizefrom the unwritten data in the buffer memory unit 120, and writes theselected data in the SLC mode to a page in the block to which new datais to be written and which has been assigned in the non-volatile memoryunit 110 (step S105).

Next, the write command processing unit 105 updates the mapping byregistering the logical address and the recording position (blockidentifier, page number, and offset in page) of the written data intothe address translation table 101A (step S106). At this time, a changeof the amount of valid data is notified from the address translationtable 101A to the valid data amount management unit 103. Thereafter, thewrite command processing unit 105 releases the area in which the writtendata has been stored in the buffer memory unit 120 (step S107).

Next, the write command processing unit 105 determines whether or notthere is a page in which no data is written, in other words, anunwritten page, in the block to which new data is to be written (stepS108). The operation mode of the block to which new data is to bewritten is the SLC mode. When there is an unwritten page (NO in stepS108), the write command processing unit 105 returns to step S104 andchecks the amount of unwritten data remaining in the buffer memory unit120. On the other hand, when there is no unwritten page (YES in stepS108), in other words, when data has been fully written to the maximumnumber of pages in the block to which new data is to be written, thewrite command processing unit 105 registers the block to which new datahas been written into the SLC block group management information 102 bof the block management unit 102 (step S109). Next, the write commandprocessing unit 105 obtains one free block managed in the free blockgroup management information 102 a of the block management unit 102, andassigns the free block as the next block to which new data is to bewritten (step S110).

Next, the write command processing unit 105 refers to the number ofblocks in the free block group in the free block group managementinformation 102 a of the block management unit 102, and determineswhether or not the number of free blocks is smaller than or equal to apredetermined threshold value Tbf (step S111). When the number of freeblocks is greater than the predetermined threshold value Tbf (NO in stepS111), the write command processing unit 105 returns to step S104. Onthe other hand, when the number of free blocks is smaller than or equalto the predetermined threshold value Tbf (YES in step S111), the writecommand processing unit 105 issues a request to reduce the number ofused blocks to the block reduction processing unit 107 and performs theused block reduction processing (step S112). Thereafter, the writecommand processing unit 105 returns to step S104.

Here, the predetermined threshold value Tbf needs to be greater than orequal to the number of blocks allocated at one time by the blockreduction processing unit 107 as the transcription destination blocks.At least one block is required as the transcription destination block,so that the predetermined threshold value Tbf needs to be greater thanor equal to one.

In FIG. 14, the processing from step S101 to step S103 can be performedin parallel with the processing of step S104 and the following steps.However, if it takes a relatively long time to perform the processing ofstep S105 and the following steps in which data is written to a page, atstep S102 in which the data storage area is allocated in the buffermemory unit 120, a sufficient size of area may not have been released.Therefore, when performing the processing from step S101 to step S103and the processing of step S104 and the following steps in parallel, itis desired to provide a step for waiting until a sufficient size of areais released in the buffer memory unit 120.

In the processing of step S104 and the following steps, it is possibleto perform in parallel the processing from step S104 to step S110 whichperforms the new data write processing and the processing from step S111to step S112 which performs the used block reduction processing.However, if there are page read operations or page write operationswhich cannot perform data access to the non-volatile memory unit inparallel, these operations need to be performed sequentially in anappropriate manner.

Here, the used block reduction processing shown in step S112 in FIG. 14will be described. In the used block reduction processing, the number ofused blocks is reduced and the number of free blocks is increased bycollecting valid data scattered in some used blocks and transcribing thevalid data to other blocks. For example, when there are M transcriptionsource blocks and the amount of valid data stored in the M transcriptionsource blocks can be stored in N transcription destination blocks, it ispossible to reduce the number of used blocks by (M−N). In this case, inthe first embodiment, used blocks in the same operation mode (SLC modeor MLC mode) are selected as the transcription source blocks. Data istranscribed to the transcription destination blocks in the MLC mode.

Hereinafter, two examples of the used block reduction processing will bedescribed. FIG. 15 is an example of collectively setting a plurality oftranscription source blocks and a plurality of transcription destinationblocks. FIG. 16A is an example of setting one transcription source blockand one transcription destination block. FIG. 16B is a modified exampleof FIG. 16A.

As shown in FIG. 15, when the block reduction processing unit 107receives a request to reduce the number of used blocks from the writecommand processing unit 105, first, the block reduction processing unit107 causes the transcription source block group selection unit 108 toperform the transcription source block group selection processing forselecting a block group to be the transcription source, in other words,the block group from which blocks are reduced, among the SLC block groupand the MLC block group managed by the block management unit 102 (stepS121). Subsequently, the block reduction processing unit 107 causes thetranscription source block selection unit 109 to perform processing forselecting M (>=1) used blocks to be transcription source in the selectedblock group as the transcription source blocks (step S122). Here, forexample, if the MLC block group is selected as the transcription sourceblock group, and the total rate of valid data of the MLC block group isV, it is possible to select M transcription source blocks whose validdata can be stored in M×V transcription destination blocks. In thiscase, by selecting an integer M satisfying M>=1/(1−V), the valid data istranscribed to N MLC blocks wherein N is an integer smaller than orequal to M−1.

Subsequently, the block reduction processing unit 107 calculates thenumber of blocks N necessary to store valid data of the selected Mtranscription source blocks to the MLC blocks, and obtains N free blocksfrom the free block group managed in the free block group managementinformation 102 a of the block management unit 102, and assigns the freeblocks as the transcription destination blocks (step S123). The numberof blocks N can be calculated by, for example, obtaining the amount ofvalid data of each of the selected M transcription source blocks fromthe valid data amount management unit 103, calculating the total amountof valid data D of all the transcription source blocks by summing up theobtained amounts of valid data, dividing the obtained total amount ofvalid data D by the block capacity Sm of the MLC block, and rounding upthe obtained value to an integer.

Next, the block reduction processing unit 107 allocates a data storagearea corresponding to at least one page in the buffer memory unit 120,and then reads valid data, which corresponds to one page, stored in theselected M transcription source blocks and outputs the read valid datato the data storage area allocated in the buffer memory unit 120 (stepS124). Subsequently, the block reduction processing unit 107 writes thevalid data read to the buffer memory unit 120 to a page of the freeblocks selected as the transcription destination blocks in the MLC mode(step S125).

Next, the block reduction processing unit 107 determines whether or notvalid data of all the M transcription source blocks has been transcribed(step S126), and when all the valid data has not been transcribed (NO instep S126), the block reduction processing unit 107 returns to step S124and transcribes the remaining valid data page by page. On the otherhand, when all the valid data has been transcribed (YES in step S126),the block reduction processing unit 107 updates the mapping of thetranscribed valid data by registering recording positions of thetranscription destination corresponding to logical addresses into theaddress translation table 101A (step S127). Based on this, all the validdata in the selected M transcription source blocks become invalid data.Subsequently, the block reduction processing unit 107 registers thetranscription source blocks from which data has been transcribed intothe free block group management information 102 a of the blockmanagement unit 102 (step S128), registers the transcription destinationblocks in which valid data is newly stored into the MLC block groupmanagement information 102 c of the block management unit 102 (stepS129), and returns to the operation shown in FIG. 14. In this way, thetranscription source blocks from which data has been transcribed arecollected as free blocks. As a result, the number of used blocks isreduced by (M−N).

On the other hand, when setting one transcription source block and onetranscription destination block, the process flow is as shown in FIG.16A. When the block reduction processing unit 107 receives a request toreduce the number of used blocks from the write command processing unit105, first, the block reduction processing unit 107 causes thetranscription source block group selection unit 108 to perform the sametranscription source block group selection processing as that in stepS121 in FIG. 15 (step S141), and then, sets “0” to the total number Bdstof transcription destination blocks (step S142). Next, the blockreduction processing unit 107 causes the transcription source blockselection unit 109 to select one used block as the transcription sourceblock from a block group selected as the transcription source (stepS143), and sets “0” to the total number Bsrc of transcription sourceblocks from which valid data has been transcribed (step S144).

Next, the block reduction processing unit 107 obtains one free blockfrom the free block group managed in the free block group managementinformation 102 a of the block management unit 102, assigns the freeblock as the transcription destination block (step S145), and incrementsby one the total number Bdst of transcription destination blocks (stepS146). It is assumed that at least one page of data storage area used bythe block reduction processing unit 107 is allocated in the buffermemory unit 120.

Next, the block reduction processing unit 107 reads valid data stored inthe transcription source block being selected and outputs the read validdata to the data storage area allocated in the buffer memory unit 120(step S147). Next, the block reduction processing unit 107 determineswhether or not all the valid data in the transcription source blockbeing selected has been read to the buffer memory unit 120 (step S148),and if all the valid data has not been read (NO in step S148), the blockreduction processing unit 107 proceeds to step S150.

As a determination result of step S148, if all the valid data in thetranscription source block has been read (YES in step S148), in the samemanner as in step S143, the block reduction processing unit 107 causesthe transcription source block selection unit 109 to select one usedblock as the transcription source block from a block group selected asthe transcription source (step S149), and proceeds to step S150. It isdesired that, when selecting new transcription source block in stepS149, the transcription source block that was selected just before thisselection is not selected again.

Next, the block reduction processing unit 107 determines whether or notthe data read to the buffer memory unit 120 becomes greater than orequal to the page size (step S150), and if the data is not greater thanor equal to the page size (NO in step S150), the block reductionprocessing unit 107 returns to step S147. On the other hand, if the datais greater than or equal to the page size (YES in step S150), the blockreduction processing unit 107 writes the valid data read to the buffermemory unit 120 to a page of the free block selected as thetranscription destination block in the MLC mode (step S151).

Next, the block reduction processing unit 107 updates the mapping of thetranscribed valid data by registering the recording position of thetranscription destination corresponding to the logical address of thetranscribed valid data into the address translation table 101A (stepS152).

Next, the block reduction processing unit 107 registers, as the freeblock group, all transcription source blocks whose amount of valid databecomes 0 among the transcription source blocks from which the validdata is transcribed in step S151 (step S153). Subsequently, the blockreduction processing unit 107 adds the number of transcription sourceblocks which become free blocks in step S153 (the number of increasedfree blocks) to the total number Bsrc of transcription source blocksfrom which valid data has been transcribed (step S154).

Next, the block reduction processing unit 107 determines whether or notdata has been fully written to the maximum number of pages of the MLCmode in the transcription destination block (step S155), and when thedata has not been fully written to the maximum number of pages (NO instep S155), the block reduction processing unit 107 returns to stepS147.

As a result of the determination in step S155, when the data has beenfully written to the maximum number of pages of the MLC mode in thetranscription destination block (YES in step S155), the block reductionprocessing unit 107 registers the transcription destination block intothe MLC block group management information 102 c of the block managementunit 102 (step S156). Subsequently, the block reduction processing unit107 determines whether or not the number of reduced blocks is greaterthan or equal to the predetermined number of reduced blocks, in otherwords, whether or not a value obtained by subtracting the total numberBdst of transcription destination blocks from the total number Bsrc oftranscription source blocks from which data has been transcribed isgreater than or equal to the predetermined number of reduced blocks(step S157), and when the number of reduced blocks is not greater thanor equal to the predetermined number of reduced blocks (NO in stepS157), the block reduction processing unit 107 returns to step S145. Onthe other hand, when the number of reduced blocks is greater than orequal to the predetermined number of reduced blocks (YES in step S157),the block reduction processing unit 107 returns to the operation shownin FIG. 14. In the manner as described above, it is also possible toreduce the intended number of used blocks.

In case that data in a transcription destination block cannot be readdue to some sort of problem during transcription, it is possible to savethe state before the transcription so that the valid data and theaddress translation table can be rolled back. FIG. 16B is a modifiedexample of FIG. 16A. In FIG. 16B, the transcription source blocks fromwhich valid data has been copied are not collected immediately as freeblocks, and the transcription source blocks are temporarily protected asa free block preparation group until data corresponding to the blockcapacity has been transcribed to the transcription destination block.When data has been transcribed to the transcription destination block,it is not necessary to save the state before the transcription. Thus,after the address translation table is updated with respect to the datathat has been transcribed, the transcription source blocks from whichdata has been transcribed are collectively collected as free blocks fromthe free block preparation group.

Steps from S141 to S151 in FIG. 16B are the same as those in FIG. 16A.Hereinafter, step S160 and the following steps will be described.

The block reduction processing unit 107 registers, as the free blockpreparation group, all transcription source blocks whose valid data hasbeen completely copied among the transcription source blocks from whichthe valid data is transcribed in step S151 (step S160).

Next, the block reduction processing unit 107 determines whether or notdata has been fully written to the maximum number of pages of the MLCmode in the transcription destination block (step S161), and when thedata has not been fully written to the maximum number of pages (NO instep S161), the block reduction processing unit 107 returns to stepS147.

As a result of the determination in step S161, when the data has beenfully written to the maximum number of pages of the MLC mode in thetranscription destination block (YES in step S161), the block reductionprocessing unit 107 registers the transcription destination block intothe MLC block group management information 102 c of the block managementunit 102 (step S162).

Next, the block reduction processing unit 107 updates the mapping of thevalid data transcribed to the transcription destination block byregistering the recording position of the transcription destinationcorresponding to the logical address of the valid data transcribed tothe transcription destination block into the address translation table101A (step S163). Then, the block reduction processing unit 107registers the blocks included in the free block preparation group as thefree block group (step S164). Subsequently, the block reductionprocessing unit 107 adds the number of transcription source blocks whichbecome free blocks in step S164 to the total number Bsrc oftranscription source blocks from which valid data has been transcribed(step S165).

Next, the block reduction processing unit 107 proceeds to step S166, andin the same manner as in step S157 in FIG. 16A, when the number ofreduced blocks is not greater than or equal to the predetermined numberof reduced blocks (NO in step S166), the block reduction processing unit107 returns to step S145. On the other hand, when the number of reducedblocks is greater than or equal to the predetermined number of reducedblocks (YES in step S166), the block reduction processing unit 107returns to the operation shown in FIG. 14.

If, as shown in FIG. 16A, the transcription source block is registeredas a free block and the free block is reused and erased before thetranscription destination block is filled with data, if, thereafter, aproblem occurs in the transcription destination block and data cannot beread from the transcription destination block, the data is lost. On theother hand, according to the flow of the processing in FIG. 16B, untilthe transcription destination block is filled with data, the same datais present in both the transcription source block and the transcriptiondestination block. Based on this, even if a problem occurs duringtranscription and data cannot be read from the transcription destinationblock, the original data remains in the transcription source block, sothat the data is not lost. In this way, in the processing flow shown inFIG. 16B, fault tolerance can be improved.

Next, the transcription source block group selection processing shown instep S121 in FIG. 15 and step S141 in FIGS. 16A and 16B will bedescribed. Some methods can be considered for the transcription sourceblock group selection processing. Hereinafter, three of those methodswill be described as examples.

FIG. 17 is an example in which the MLC block group is preferentiallyselected as the transcription source block group when the rate of validdata of the MLC block group is lower than a predetermined thresholdvalue. FIG. 18 is an example in which a block group having the lowerrate of valid data is selected from the SLC block group and the MLCblock group as the transcription source block group. FIG. 19 is anexample in which limitations of the number of blocks Bm and the rate ofvalid data Vm of the MLC block group shown in FIG. 17 are added to theexample shown in FIG. 18.

As shown in FIG. 17, the transcription source block group selection unit108 obtains the total number of blocks Bm in the MLC block group byreferring to the MLC block group management information 102 c of theblock management unit 102 (step S201), obtains the amount of valid datain each MLC block belonging to the MLC block group from the valid dataamount management unit 103, and calculates the total amount of validdata Dm in all the MLC blocks by summing up the obtained amounts ofvalid data (step S202), and subsequently as shown by the formula 1below, the transcription source block group selection unit 108calculates the total rate of valid data Vm of the MLC block group bydividing the total amount of valid data Dm obtained in step S202 by avalue obtained by multiplying the total number of blocks Bm obtained instep S201 by the capacity of one MLC block Sm (step S203).

Vm=Dm/(Bm*Sm)  (1)

Next, the transcription source block group selection unit 108 determineswhether or not the total number of blocks Bm in the MLC block group issmaller than or equal to a predetermined threshold value Tbm (stepS204), and if the total number of blocks Bm is greater than thethreshold value Tbm (NO in step S204), the transcription source blockgroup selection unit 108 subsequently determines whether or not thetotal rate of valid data Vm of the MLC block group is greater than apredetermined threshold value Tvm (step S205).

When the total number of blocks Bm is smaller than or equal to thethreshold value Tbm (YES in step S204), or when the total rate of validdata Vm is greater than the threshold value Tvm (YES in step S205), thetranscription source block group selection unit 108 selects the SLCblock group as the transcription source block group (step S206). On theother hand, when the total number of blocks Bm is greater than thethreshold value Tbm and when the total rate of valid data Vm is smallerthan or equal to the threshold value Tvm (NO in step S204 and NO in stepS205), the transcription source block group selection unit 108 selectsthe MLC block group as the transcription source block group (step S207).When selecting the transcription source block group in this way, thetranscription source block group selection unit 108 returns to theoperation shown in FIG. 15, 16A, or 16B, and returns the processing tothe block reduction processing unit 107.

For example, the threshold value Tvm is desired to be a value that makestranscription efficiency not worse than that in a case in which all theblocks are MLC blocks. The transcription efficiency is worst when thelogical capacity of valid data provided to the host is fully recorded,and the valid data is evenly distributed and stored in all the blocks.In this case, when the total storage capacity is represented by Sall,and the logical capacity is represented by Smax, the rate of valid dataV of each block is represented by V=Smax/Sall. Here, when thetranscription is performed, by transcribing M transcription sourceblocks (M=1/(1−V)) to N transcription destination blocks (N=M−1), thenumber of used blocks can be reduced by one. Therefore, when thethreshold value Tvm=V, if the total rate of valid data Vm of the MLCblock group is smaller than or equal to the threshold value Tvm, it ispossible to reduce the number of used blocks by one when at least Mtranscription source blocks are transcribed, so that the transcriptionefficiency is not worse than the worst case described above.

As described above, according to the transcription source block groupselection unit 108 shown in FIG. 17, the number of blocks in the MLCblock group can be reduced in a range in which the transcriptionefficiency is not worse than a value determined by the threshold valueTvm, so that the reduced number of blocks can be assigned as the SLCblocks.

When a block group having the lower rate of valid data is selected fromthe SLC block group and the MLC block group as the transcription sourceblock group, as shown in FIG. 18, in the same manner as in steps S201 toS203 in FIG. 17, the transcription source block group selection unit 108calculates the total rate of valid data Vm.

Also, the transcription source block group selection unit 108 obtainsthe total number of blocks Bs in the SLC block group by referring to theSLC block group management information 102 b of the block managementunit 102 (step S221), obtains the amount of valid data in each SLC blockbelonging to the SLC block group from the valid data amount managementunit 103, and calculates the total amount of valid data Ds in all theSLC blocks by summing up the obtained amounts of valid data (step S222),and subsequently as shown by the formula 2 below, the transcriptionsource block group selection unit 108 calculates the total rate of validdata Vs of the SLC block group by dividing the total amount of validdata Ds obtained in step S222 by a value obtained by multiplying thetotal number of blocks Bs obtained in step S221 by the capacity of oneSLC block Ss (step S223). Here, when the SLC mode is two-value mode andthe MLC mode is four-value mode, the capacity of SLC block Ss is ½ ofthe capacity of MLC block Sm.

Vs=Ds/(Bs*Ss)  (2)

Next, the transcription source block group selection unit 108 comparesthe total rate of valid data Vm of the MLC block group calculated instep S203 and the total rate of valid data Vs of the SLC block groupcalculated in step S223 (step S224), and when the total rate of validdata Vs of the SLC block group is smaller than or equal to the totalrate of valid data Vm of the MLC block group (YES in step S224), thetranscription source block group selection unit 108 selects the SLCblock group as the transcription source block group (step S206). On theother hand, when the total rate of valid data Vs is greater than thetotal rate of valid data Vm (NO in step S224), the transcription sourceblock group selection unit 108 selects the MLC block group as thetranscription source block group (step S207). When selecting thetranscription source block group in this way, the transcription sourceblock group selection unit 108 returns to the operation shown in FIG.15, 16A, or 16B, and returns the processing to the block reductionprocessing unit 107.

As described above, according to the processing flow of thetranscription source block group selection unit 108, a block grouphaving the lower rate of valid data is selected from the SLC block groupand the MLC block group as the transcription source block group. Thus,compared with the processing flow shown in FIG. 17, although the amountof calculation of the total rate of valid data increases, thetranscription efficiency can be improved.

When calculating the total rate of valid data of the SLC block group andthe MLC block group by simply assuming that the capacity of SLC block isthe same as the capacity of MLC block, the SLC block group, which canoriginally store therein only a half of valid data that can be stored inthe MLC block group, tends to be selected. On the other hand, whencalculating the total rate of valid data of the SLC block group byassuming that the capacity of SLC block Ss is ½ of the capacity of MLCblock Sm, it is possible to prevent the SLC block group from tending tobe selected.

Further, when limitations of the number of blocks Bm and the rate ofvalid data Vm of the MLC block group shown in FIG. 17 are added to theexample shown in FIG. 18, as shown in FIG. 19, in the same manner as insteps S201 to S203 shown in FIG. 17, the transcription source blockgroup selection unit 108 calculates the total rate of valid data Vm ofthe MLC block group, and then, in the same manner as in steps S204 andS205 shown in FIG. 17, determines whether or not the total number ofblocks Bm in the MLC block group is smaller than or equal to apredetermined threshold value Tbm (step S204), and if the total numberof blocks Bm is greater than the threshold value Tbm (NO in step S204),the transcription source block group selection unit 108 subsequentlydetermines whether or not the total rate of valid data Vm of the MLCblock group is greater than a predetermined threshold value Tvm (stepS205).

When the total number of blocks Bm is smaller than or equal to thethreshold value Tbm (YES in step S204), or when the total rate of validdata Vm is greater than the threshold value Tvm (YES in step S205), thetranscription source block group selection unit 108 selects the SLCblock group as the transcription source block group (step S206). On theother hand, when the total number of blocks Bm is greater than thethreshold value Tbm and when the total rate of valid data Vm is smallerthan or equal to the threshold value Tvm (NO in step S204 and NO in stepS205), in the same manner as in steps S221 to S223 shown in FIG. 18, thetranscription source block group selection unit 108 calculates the totalrate of valid data Vs of the SLC block group. Then, the transcriptionsource block group selection unit 108 compares the total rate of validdata Vm of the MLC block group calculated in step S203 and the totalrate of valid data Vs of the SLC block group calculated in step S223(step S224), and when the total rate of valid data Vs of the SLC blockgroup is smaller than or equal to the total rate of valid data Vm of theMLC block group (YES in step S224), the transcription source block groupselection unit 108 selects the SLC block group as the transcriptionsource block group (step S206). On the other hand, when the total rateof valid data Vs is greater than the total rate of valid data Vm (NO instep S224), the transcription source block group selection unit 108selects the MLC block group as the transcription source block group(step S207). When selecting the transcription source block group in thisway, the transcription source block group selection unit 108 returns tothe operation shown in FIG. 15, 16A, or 16B, and returns the processingto the block reduction processing unit 107.

In the transcription source block group selection processing shown inFIG. 18, for example, when the total number of blocks Bm in the MLCblock group is one and the total amount of valid data Dm is one cluster,the total rate of valid data Vm of the MLC block group is very low, sothat the MLC block group may be selected as the transcription source. Insuch a case, even when the MLC block group is selected as thetranscription source, the number of used blocks cannot be reduced. Also,both the total rates of valid data Vs and Vm may be near 100%. As anextreme example, there is a case in which, for example, both the numbersof blocks Bs and Bm are 100, the total rate of valid data Vs is 100%,and the total rate of valid data Vm is 99%. In this case, in thetranscription source block group selection processing shown in FIG. 18,the MLC block group is selected as the transcription source. As aresult, to reduce one block, it is necessary to select 100 MLC blocks asthe transcription source and select 99 free blocks as the transcriptiondestination. Therefore, as shown in FIG. 19, by adding limitations tothe number of blocks Bm and the rate of valid data Vm of the MLC blockgroup, even when Vs>Vm, the SLC block group is selected as thetranscription source.

FIG. 20 shows a simulation result of random write. The X axis of FIG. 20indicates the size of access range, in other words, indicates locality,and the range is 0 to the logical capacity. The Y axis indicates randomwrite performance with respect to data of 4 KB, the unit of performanceis IOPS. In FIG. 20, the solid line L1 is a curve showing the randomwrite performance of the memory system 1, and the dashed line L2 is acurve showing the random write performance of a conventional memorysystem that uses all blocks in the MLC mode. As obvious from FIG. 20, inthe memory system 1, random write performance better than that of theconventional memory system can be obtained, in particular, in a rangewith high locality.

As described above, according to the first embodiment, in an accesspattern with strong locality, data that is not updated frequently isdivided into the MLC block and data that is updated frequently isdivided into the SLC block, so that it is possible to improve long-termtranscription efficiency. When the total amount of valid data is small,it is possible to reduce useless transcription of the SLC blocks andincrease the cache effect of the SLC blocks with high access speed. Inaddition, by dynamically selecting the operation mode of the free block,it is possible to obtain the merit of SLC flash memory and the merit ofMLC flash memory depending on the situation.

Next, a memory system 2 according to a second embodiment will bedescribed in detail with reference to the drawings. In the secondembodiment, the execution of the used block reduction processing shownin step S112 in FIG. 14 is triggered when a command such as read, write,flush, and deletion of data is not received from the host device 150 fora certain period of time, and when a transcription of data is requestedfrom the host device 150, in addition to when the number of free blocksis smaller than or equal to a predetermined threshold value Tbf (YES instep S111 in FIG. 14).

As obvious from comparison between FIG. 21 and FIG. 5, the memory system2 according to the second embodiment includes a timer 201 in addition tothe same configuration as that of the memory system 1 shown in FIG. 5.The timer 201 is configured by an up-counter, and when the count valueis greater than or equal to a predetermined value, the timer 201 sends aused block reduction request to the block reduction processing unit 107.The block reduction processing unit 107 performs the used blockreduction processing shown in FIG. 15, 16A, or 16B in accordance withthe request.

FIG. 22 is a flowchart showing a schematic operation when the used blockreduction processing is performed on the basis of the count value of thetimer. As shown in FIG. 22, the block reduction processing unit 107starts the timer 201 (step S301), and thereafter, for example at regularintervals, determines whether or not a command is received from the hostdevice 150 (step S302). When a command is not received (NO in stepS302), the block reduction processing unit 107 determines whether or nota count value H of the timer 201 is greater than or equal to apredetermined threshold value Tt (step S303). When the count value H issmaller than the threshold value Tt (NO in step S303), the blockreduction processing unit 107 directly returns to step S302. On theother hand, when the count value H is greater than or equal to thethreshold value Tt (YES in step S303), the block reduction processingunit 107 resets the timer 201 (step S304). Thereafter, in the samemanner as in step S112 in FIG. 14, the block reduction processing unit107 performs the used block reduction processing (step S307), and thenreturns to step S302.

When a command is received from the host device 150 (YES in step S302),the block reduction processing unit 107 resets the timer 201 (stepS305), and subsequently determines whether or not the received commandis the used block reduction request (step S306). When the receivedcommand is not the used block reduction request (NO in step S306), theblock reduction processing unit 107 directly returns to step S302. Onthe other hand, when the received command is the used block reductionrequest (YES in step S306), in the same manner as in step S112 in FIG.14, the block reduction processing unit 107 performs the used blockreduction processing (step S307), and then returns to step S302.

As described above, according to the second embodiment, when a commandis not sent from the host for a certain period of time, it is estimatedthat the period in which command is not sent will continue, so that theused block reduction processing can be performed during the period.Regarding the command for instructing reduction of the number of usedblocks, it can be expected that the host sends the command on the basisthat the host recognizes that the host will not access data for a while.Therefore, although the used block reduction processing cannot bereduced in total, by performing the used block reduction processing inadvance during a period in which the host does not access data, it ispossible to reduce the used block reduction processing that should beperformed in parallel with writing from the host and suppressdegradation of the transmission performance when the host writes data.Other configurations, operations, and effects are the same as those ofthe first embodiment, so that the detailed description thereof will beomitted.

While certain embodiments have been described, these embodiments havebeen presented by way of example only, and are not intended to limit thescope of the inventions. Indeed, the novel embodiments described hereinmay be embodied in a variety of other forms; furthermore, variousomissions, substitutions and changes in the form of the embodimentsdescribed herein may be made without departing from the spirit of theinventions. The accompanying claims and their equivalents are intendedto cover such forms or modifications as would fall within the scope andspirit of the inventions.

1-20. (canceled)
 21. A method of controlling a memory system including anon-volatile semiconductor memory having a plurality of first storageareas, the first storage areas being capable of including one or moresecond storage areas, a plurality of third storage areas in which datais written in a first mode, and a plurality of fourth storage areas inwhich data is written in a second mode, the first mode being differentfrom the second mode; the method comprising: performing a used blockreduction processing that repeatedly performs: acquiring one or moresecond storage areas from the plurality of first storage areas;selecting a plurality of storage areas from the plurality of thirdstorage areas or from the plurality of fourth storage areas, when anelapsed time measured by a timer reaches a specific time or when aperiod without access from a host reaches a specific time; writing thevalid data stored in the selected plurality of storage areas in theacquired one or more second storage areas using the second mode;obtaining a number of reduced blocks by subtracting a total number ofthe selected plurality of storage areas from a total number of theacquired second storage areas; and determining whether the number ofreduced blocks is greater than or equal to a predetermined number, andterminating, when the number of reduced blocks is greater than or equalto the predetermined number, the used block reduction processing. 22.The method according to claim 21, wherein a write speed or a read speedof the second mode is slower than that of the first mode.
 23. The methodaccording to claim 21, wherein a maximum write data amount per unit areaof the second mode is greater than that of the first mode.
 24. Themethod according to claim 21, wherein the one or more second storageareas are areas without valid data, the plurality of third storage areasare areas where data write requested from a host is written, theplurality of fourth storage areas are areas where data having beenstored in the third storage areas is rewritten, the acquiring includesacquiring the one or more second storage areas based on first managementinformation, and the selecting includes selecting the plurality ofstorage areas from the plurality of third storage areas based on secondmanagement information or selecting the plurality of storage areas fromthe plurality of fourth storage areas based on third managementinformation such that the selection is limited to either third storageareas or fourth storages areas, but not both, and the method furthercomprising deleting, when the valid data stored in the selected storageareas is written in the acquired second storage areas, the selected oneor more storage areas from the second management information or thethird management information, and adding the one or more second storageareas where the valid data is written in the first managementinformation.
 25. The method according to claim 24, wherein the validdata is data stored in a physical address associated with a logicaladdress, the first management information indicates which area among theplurality of first storage areas is the second storage area, the secondmanagement information indicates which area among the plurality of firststorage areas is the third storage area, and the third managementinformation indicates which area among the plurality of first storageareas is the fourth storage area.
 26. The method according to claim 25,the memory system further including: a first storage configured to storethe first management information; a second storage configured to storethe second management information; and a third storage configured tostore the third management information, wherein the logical address isan address specified by the host, and the physical address indicates astorage position of data in the storage areas of the semiconductormemory.
 27. The method according to claim 21, the memory system furtherincluding a plurality of the semiconductor memories, wherein the methodfurther comprising executing parallel data transfer with respect to theplurality of semiconductor memories.
 28. The method according to claim24, wherein, the selecting includes selecting the plurality of storageareas from the plurality of third storage areas in the order of writingbased on the second management information.
 29. The method according toclaim 21, wherein the selecting includes selecting the plurality ofstorage areas at one time, and the acquiring includes acquiring the oneor more second storage areas at one time, the one or more second storageareas being one or more write targets of the valid data stored in theselected storage areas.
 30. The method according to claim 21, whereinthe acquiring includes acquiring the one or more second storage areasone by one, the one or more second storage areas being one or more writetargets of the valid data stored in the selected storage areas, and theselecting includes selecting the plurality of third storage areas or theplurality of fourth storage areas one by one, which store the valid datato be written in the acquired one or more second storage areas.
 31. Themethod according to claim 24, the method further comprising suspendingthe deletion of the selected plurality of storage areas from the secondmanagement information or the third management information untilcompletion of writing the valid data into the acquired one or moresecond storage areas.
 32. The method according to claim 25, the memorysystem further including an address mapping table configured to manage acorrespondence relationship between the logical address and the physicaladdress, wherein the address mapping table includes a reverse tablecapable of searching a logical address of each entry based on a storageposition of each entry.
 33. The method according to claim 21, furthercomprising measuring the elapsed time by the timer.
 34. The methodaccording to claim 33, further comprising restarting the timer inresponse to performing the used block reduction processing.
 35. Themethod according to claim 33, further comprising resetting the timer inresponse to an access from the host.
 36. The method according to claim21, wherein the selecting includes selecting, when the number of thefourth storage areas is equal to or smaller than a first threshold valueor when a total rate of valid data in the fourth storage areas isgreater than a second threshold value, the plurality of storage areasfrom the plurality of third storage areas, and selecting, when thenumber of the fourth storage areas is greater than the first thresholdvalue and the total rate of valid data in the fourth storage areas isequal to or smaller than the second threshold value, the plurality ofstorage areas from the fourth storage areas, and the total rate of validdata in the fourth storage areas is a rate of the total amount of validdata stored in the fourth storage areas with respect to the totalcapacity of the fourth storage areas.
 37. The method according to claim21, wherein the selecting includes selecting, when a total rate of validdata in the third storage areas is equal to or smaller than a total rateof valid data in the fourth storage areas, the plurality of storageareas from the third storage areas, and selecting, when the total rateof valid data in the third storage areas is greater than the total rateof valid data in the fourth storage areas, the plurality of storageareas from the fourth storage areas, the total rate of valid data in thethird storage areas is a rate of the total amount of valid data storedin the third storage areas with respect to the total capacity of thethird storage areas, and the total rate of valid data in the fourthstorage areas is a rate of the total amount of valid data stored in thefourth storage areas with respect to the total capacity of the fourthstorage areas.
 38. The method according to claim 37, further comprisingcalculating the total rate of valid data in the third storage areas andthe total rate of valid data in the fourth storage areas on the basis ofa block capacity according to an operation mode of each block.
 39. Themethod according to claim 21, wherein all of the plurality of firststorage areas are configured to accept write operation in both of thefirst mode and the second mode.
 40. The method according to claim 21,wherein the performing includes performing the used block reductionprocessing in parallel with the write operation in response to a requestfrom a host.